- User Capabilities
- Credential Capabilities
- All User Checksum
- User Get/Report
- Credential Get/Report

Merged :
UIC-3222: Fix Supported Credential Types
UIC-3222: Ignore User ID 0 & don't create duplicates
UIC-3222: Delayed interview
UIC-3222: User Credential User Name Encoding under UUID (No real advantage to put this under USER_NAME)
UIC-3222: Fix user discovery
UIC-3222: Credential get log
UIC-3222: Discovery fix (credential and user get)
UIC-3222: Discovery interview remove all users before user interview
UIC-3222: Fix credential report if credential data is missing
UIC-3222: Remove user if User modifier type is DNE
UIC-3222: Correctly remove all user credential before discovery
UIC-3222: set_reported_attribute return correct status and undefined desired
UIC-3222: Add get_desired user id node function
UIC-3222: get_credential_type can now be searched as desired value
UIC-3222: Credential Learn Properties

[Philippe Coval]

Adjusted crc16 in applications/zpc/components/zwave_command_classes/test/CMakeLists.txt

UIC-3222: Credential Set on Credential Operation Type
UIC-3222: Set Credential (delete) improvement
UIC-3222: Credential SET also look in desired values

UIC-3222: Fix delete operation on Credential SET
UIC-3222: Allow extra bytes when testing set/get commands

UIC-3222: User set on User Operation Type
UIC-3222: More user types
UIC-3222: User SET fix
UIC-3222: Set User (delete) improvement
UIC-3222: Fix expiring minutes to Desired Or Reported to allow add
UIC-3222: User SET can look into desired attributes

UIC-3222: Expose New credential capabilities
UIC-3222: Expose Admin Code

[Philippe Coval]

Adjusted applications/zpc/components/zwave_command_classes/test/CMakeLists.txt

…al capabilities update

This patch will :
- Not delete all user database en Unify startup
- Allow the user to re-initiate an interview with the device and discover again all users

Also remove credential if modifier type is DNE

UIC-3222: Documentation of delete all credentials

In the previous implementation of U3C, User Notification Report size was incorrect : Z-Wave-Alliance/z-wave-stack#409
This commit use the correct implementation.

This commit will ensure that no more than Credential Type/Credential Slot exists no matter the user that got it. If we have (1,1) credential for User 1, user 2 cannot have a credential with type 1 and slot 1. User 2 should have type 1 and slot 2.

For more context see Z-Wave-Alliance/AWG#172

Verify that the slot we are trying to add is in range of supported slots

This will make the User Credential Implementation clearer

Add a new helper class for clarity

Much simpler and more efficient thanks to change parent feature

Top level API is now available directly with an header to avoid base file to be too big

Use new C++ api to be more consistent

0 nodes are better handled
Credential node are properly deleted when no credential is available

Only check reported value instead of desired and reported
Updated test to better coverage USER_SET

…rules

Works both when adding a credential and modifying it

Use a new callback mechanism that allows the server to listen to certain event

Add a notification to the UI
Set the received checksum last

Allow to add an credential that is already in the node tree
Check desired or reported value of CREDENTIAL_LEARN_OPERATION_TYPE to avoid issues with supervision
Send status to mqtt

Now the attribute ALL_USERS_CHECKSUM is defined at the end of the User interview if device support it
Add command to force the refresh of the checksum

…mmands

Now correctly interview ALL users on the first discovery (previously was only checking the first one due to a resolution error)
All user checksum happens after all users & all credentials are reported

Feel free to stress test by doing negative testing and changes
usernames (using spaces or escapes).

May delete commands produce retained events.

Further negative testing will not hurt.

Relate-to: SiliconLabsSoftware#144
Signed-off-by: Philippe Coval <[email protected]>